Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding ability to send cloud-init user-data to triton machines #12840

Closed
wants to merge 1 commit into from

Conversation

zero-below
Copy link

In Joyent's images, at least for ubuntu, user-data is used for joyent infrastructure and cloud-init needs to be uploaded to cloud-init:user-data instead of just user-data.

See notes in: https://docs.joyent.com/public-cloud/instances/virtual-machines/images/linux/ubuntu-certified#cloud-init-examples

Cloud-init data is provided as metadata with the cloud-init:user-data key. Joyent boot-time data is supplied as metadata with the user-data and user-script keys.

I've built and tested this in my own infrastructure in joyent, with v0.9.0. This successfully placed the key onto the machine, and a basic cloud-config template was applied.

#cloud-config
write_files:
-   content: test123
    owner: root:root
    path: /tmp/testfile123
    permissions: '0644'
EOF
ubuntu@dev-infra-01:~$ cat /tmp/testfile123 
test123ubuntu@dev-infra-01:~$

…out of a key called cloud-init:user-data, as opposed to to the standard user-data. This will make it possible to send the cloud-config data to triton machines.
@jen20
Copy link
Contributor

jen20 commented Apr 28, 2017

@zero-below Thanks for opening a pull request! I'm going to pull this down to rebase it and test locally prior to merging.

@jen20
Copy link
Contributor

jen20 commented Apr 28, 2017

This has been merged in fcddc1d. Thanks @zero-below!

@jen20 jen20 closed this Apr 28, 2017
@ghost
Copy link

ghost commented Apr 13, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants